Skip to content

chore: add Datadog Code Coverage upload, remove CodeCov#707

Draft
nikita-tkachenko-datadog wants to merge 2 commits into
DataDog:mainfrom
nikita-tkachenko-datadog:nikita.tkachenko/serverless-plugin-datadog-add-dd-coverage
Draft

chore: add Datadog Code Coverage upload, remove CodeCov#707
nikita-tkachenko-datadog wants to merge 2 commits into
DataDog:mainfrom
nikita-tkachenko-datadog:nikita.tkachenko/serverless-plugin-datadog-add-dd-coverage

Conversation

@nikita-tkachenko-datadog

Copy link
Copy Markdown

Onboard to Datadog Code Coverage and remove CodeCov upload.

Summary

  • Removes the codecov/codecov-action step from the test job in .github/workflows/build.yml
  • Adds a Datadog Code Coverage upload step using @datadog/datadog-ci after tests run, gated on matrix.node-version == 24 to avoid duplicate uploads from the matrix build
  • Jest already generates coverage/lcov.info via the lcovonly reporter in jest.config.js — no test command changes needed

Test plan

  • Confirm DATADOG_API_KEY secret is set in the repository settings
  • Verify coverage appears in Datadog Code Coverage for the serverless-plugin-datadog service after merging

nikita-tkachenko-datadog and others added 2 commits June 17, 2026 12:27
Replace the codecov/codecov-action upload step with Datadog Code Coverage
upload via @datadog/datadog-ci. Coverage is already generated by Jest with
the lcovonly reporter (coverage/lcov.info). Upload runs only on node 24 to
avoid duplicate uploads from the matrix build.

Environment: Datadog workspace

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The datadog-ci coverage upload command does not support a --service flag.
Use the DD_SERVICE env var instead, and add continue-on-error so fork
PRs without the DATADOG_API_KEY secret do not fail CI.

Environment: Datadog workspace

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant